Hi!I'm in the process of setting up a new SCCM system. So far I have successfully installed a primary site (S01) and two secondary sites (S02 & S03) for two different geographic locations. The primary site consists of one Central Site Server and one dedicated server for the PXE service point for that site. The secondary sites are installed on dedicated servers and each one have its own WDS/PXE service point.Now I have started to verify the OSD functionality for all the sites to see that it works like it should. The primary site is delivering the OSD functionality like expected. The first (S02) of the two secondary sites that I have started to verify is giving me the following error: "No DHCP or proxyDHCP offers were received". I have seen this error before and I think it usually means the network is not realying the DHCP traffic correctly between thesubnets. The funny thing here is that the old WDS, in this domain, is working properly when I bootmy VMWare test client. I get anIP and WinPE starts booting right away. But when I shut down the old WDS and activate the new PXE service point it doesn't work any more when booting from the same test client. How come? Based on this I get the feeling that there is nothing wrong with the network. What else could it be?The new Windows Deployment Server has been authorized in the local DHCP server. The Boot images (32 bit/64 bit) has been distributed to all sites and PXE service points. The same goes for the Vista media.Any help on this would be very much appreciated.Regards,Fredrik

I just realized that this question probably belong to the OSD section of the forum.

The funny thing here is that the old WDS, in this domain, is working properly when I bootmy VMWare test client. I get anIP and WinPE starts booting right away. But when I shut down the old WDS and activate the new PXE service point it doesn't work any more when booting from the same test client. How come? Based on this I get the feeling that there is nothing wrong with the network. What else could it be? Moved to the OSD subforum for your convenience :-)Are the PXE SP and the old WDS server on the same subnet? Maybe there are DHCP options or IPhelpers set that point to the old WDS box?

The funny thing here is that the old WDS, in this domain, is working properly when I bootmy VMWare test client. I get anIP and WinPE starts booting right away. But when I shut down the old WDS and activate the new PXE service point it doesn't work any more when booting from the same test client. How come? Based on this I get the feeling that there is nothing wrong with the network. What else could it be? Moved to the OSD subforum for your convenience :-)Are the PXE SP and the old WDS server on the same subnet? Maybe there are DHCP options or IPhelpers set that point to the old WDS box? Thanks!I don't know for sure wether the they are on the same subnet or not. This is one thing that I will investigate further. Earlier when Ibrowsed the scope options for the DHCP I noticed that the option 060 PXEClient was present, but unmarked. Don't knowif that has anything to do with it.

Options 66 and 67 have to be used (unsupported) or IPhelpers on your network devices.

Hi Torsten,I solved the problem!When I removed the 060 PXEClient from the scope option on the DHCP, the reference machine booted WinPE right away. Neither one of the 66 or 67 option was enabled.

Should the 060 PXEClient option be set when using IP helpers to forward DHCP/PXE requests also to the PXE/WDS server? Regards